Exclude opentelemetrybot/**/* from branch creation restriction #13636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
semantic-conventions-javaprepare-release-branchworkflow failed because it tried to create a branch restricted by the repo rulesets.I added an exclusion of
opentelemetrybot/**/*to get release back on track, but found thatsemantic-conventions-javareferences this repo'srepository-settings.mdas its source of truth.It appears that this repo uses a release branch name pattern of
otelbot/**/*, which is out of sync withopentelemetry-javaandsemantic-conventions-java. An alternative would be to update those two repos to use the name release branch naming pattern ofopentelemetry-java-instrumentation.